Importing EDI

Configuration Process Importing EDI files via the Import EDI form Importing orders from the web FAQ & Diagnostic Tips Why are two different CSV EDI import order files with the same values failing on the same field in my EDI Import History? During import of EDI orders, why do I receive a 'Lookup failed in table' note? After opening an EDI Sales Order Import .csv file in Excel and re-saving, my import file fails during import. On EDI Sales Order Imports, I have a condition to pull in the price from the order, but the price still defaults to the system price. Tips:

EDI stands for “Electronic Data Interchange”. The EDI process involves using computers to complete transactions electronically between two organizations, called “Trading Partners”. Deacom provides a highly flexible and configurable EDI solution allowing companies to maximize the value of implementing EDI transactions. Any outbound transaction can be configured within Deacom. A list of Deacom-supported inbound and traditional outbound EDI transactions including additional information on the EDI process in Deacom is available via EDI Imports.

The importing EDI process covered on this page is performed after EDI import profiles have been created.

Configuration

Prior to performing EDI Imports in Deacom, users must first create EDI Import profiles via System > Maintenance > EDI Imports. Once the profile have been saved, users may then run the EDI imports by using this transaction. Refer to Configuring Inbound EDI Transactions for process information. The security setting, "System -- edi imports" controls which users have access to EDI Imports.

Note: If users do not require access to the System > Maintenance area, a Favorite can be created for the EDI Import option, and the security setting "System Menu" can be set to "No."

Process

Importing EDI files via the Import EDI form

• Once users navigate to the Tools > Import EDI transaction they will be presented with the "Import EDI" form. This form is used to run the EDI Import profiles that were created previously.
• The form contains two columns, one containing the name of the EDI Import and the other whether or not the EDI is set to run. All EDI imports are set to run by default. The "Select All" and "Clear All" buttons will set the run value to "Yes" and "No" respectively for all imports. Users may also double click the name of the EDI import to change the value in the "Run" column from "Yes" to "No" and vice versa.
• Once the correct imports have been set to "Yes", the "Run" button, located at the bottom left of the "Import EDI" form is used to begin the import process.
• Once all the imports have completed, the system will display a message indicating how many orders were created as a result.
• The order numbers that were created will be displayed in the History / Performance report (versions 15.03.051 and above) or the View EDI Import History report (versions 15.03.032 and below). Users may also use the different fields on the Sales > Order Reporting pre-filter to isolate the orders that were created as a result of the EDI imports.
• Once the import has been completed, orders may be processed normally.

In cases were the EDI imports were not successful, the system will indicate that "0" orders were created. The EDI Import History log, as mentioned previously may be used to diagnose EDI import issues.

Importing orders from the web

Many organizations choose the import sales orders directly from a form on their website. The process is similar to a standard EDI import in Deacom with the import file being created by the website. The process is outlined below.

• Gather the required information through a form on the website.
• Save the information from the website into an XML file, tab delimited text file or Excel file. This file should be saved in a specific file directory on the server so that Deacom can grab it.
• Run the Deacom EDI process to upload the file as a sales order.

FAQ & Diagnostic Tips

Why are two different CSV EDI import order files with the same values failing on the same field in my EDI Import History?

This can be the result of opening a CSV file in Excel, making a change and saving. Excel re-formats the numeric values on CSV files. As a result, the system is not searching for the correct value during look-ups in the system when importing the file. Edit CSV files in non-excel programs like Notepad and Notepad + + to avoid values being altered.

During import of EDI orders, why do I receive a 'Lookup failed in table' note?

Lookup failures are often an indication that information provided on the import file is either incorrect or not set up in the Deacom environment. Generally, lookup failure notifications give precise reasons as to why an import failed. If needed, utilize the Expression and the Search Value provided on the notification window for further troubleshooting. System > Data Dictionary and System > Query are also valuable tools.

After opening an EDI Sales Order Import .csv file in Excel and re-saving, my import file fails during import.

It is best to edit .csv import files in a non-excel program like Notepad, Notepad ++ or CSVed as excel can change the format cells. For example, the number 0720724320052 can get changed to 7.20724E + 11, which will fail in a lookup.

On EDI Sales Order Imports, I have a condition to pull in the price from the order, but the price still defaults to the system price.

To use manual pricing, a Method of Pricing parsing rule must be set up. In System > Maintenance > EDI Imports, add the following Parsing Rule to your Import setup:

• Field: Method of pricing
• Type: Expression
• Field Expression: ‘Manual’

Tips:

• When shipping sales orders, processing EDI files can reserve lots before shipping those lots.
• Date Calcs, which are located in Sales > Options and Purchasing > Options are fired after the EDI Import map has completed it's import.
• Beginning in version 17.00.018, when importing a file with a name that already exists, the system will use a military time timestamp when appending to the file name. For example, 1pm will be noted as "130000", not "010000".